Conversation
|
This PR will trigger a patch release when merged. |
src/support/edge-routing-utils.js
Outdated
| import { calculateForwardedHost } from '@adobe/spacecat-shared-tokowaka-client'; | ||
|
|
||
| // Supported CDN / log source types. Aligned with auth-service (cdn-logs-infrastructure/common.js). | ||
| export const LOG_SOURCES = { |
There was a problem hiding this comment.
I'd suggest keeping LOG_SOURCES in llmo-utils only. May be rename them as CDN_TYPES
src/controllers/llmo/llmo.js
Outdated
|
|
||
| // CDN routing — only when cdnType is provided | ||
| if (cdnTypeNormalized) { | ||
| // Authorization: LLMO Administrator (paid) OR member of LLMO Admin IMS group (trial). |
There was a problem hiding this comment.
check for cs fastly required (by dig)
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
| throw err; | ||
| } | ||
|
|
||
| let isGroupMember = false; |
There was a problem hiding this comment.
Good to have: Group membership check should go in ims client
There was a problem hiding this comment.
Will take this up in next PR if thats okay.
| // The import worker handler iterates all opted-in sites and stamps edgeOptimizeConfig.enabled | ||
| // when Tokowaka confirms the site is serving edge-optimized content. | ||
| export const OPTIMIZE_AT_EDGE_ENABLED_MARKING_TYPE = 'optimize-at-edge-enabled-marking'; | ||
|
|
There was a problem hiding this comment.
This is being duplicated. Better to move it to shared pkg.
There was a problem hiding this comment.
Will take this up in a next PR if thats okay.
# [1.432.0](v1.431.0...v1.432.0) (2026-04-10) ### Features * AEMCS fastly Edge Routing Automation ([#2127](#2127)) ([56be44e](56be44e))
|
🎉 This PR is included in version 1.432.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Please ensure your pull request adheres to the following guidelines:
describe here the problem you're solving.
If the PR is changing the API specification:
yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet.
If the PR is changing the API implementation or an entity exposed through the API:
If the PR is introducing a new audit type:
Related Issues
Thanks for contributing!